OpenEdge Development:<br />Progress Dynamics Web Development Guide Client-side features

The sections that follow briefly describe the client-side features in Progress Dynamics that enable the development of Web applications.

Static files

A number of static files implement DHTML in Progress Dynamics. The static files do not exist in the Progress Dynamics Repository, but are installed either in a Web Server’s Document Root directory or in install_dir\tty\dynamics\ry\. (Note that although these files are stored on the server, they are sent to and run on the client.)

HTML layout file — The HTML layout file (default.htm) provides a starter page layout that includes a menu bar, a tool bar, a tree view, a message area, and hidden frames for client/server communications.

Cascading Style Sheets — Two CSS files (rymain.ccs and ryapp.css) contain default style settings that you can inherit, modify, or override.

JavaScript object files — A number of JavaScript files make up a library of event handlers, methods, and properties that you can inherit, modify, or override.

Utilities — A number of HTML files provide utilities, such as pop-up calculators and calendars, that you can embed in your application.

Images — Images include a number of .gif and .jpg files that you can use for buttons and tools.

JavaScript API

The JavaScript API contains a variety of methods that allow you to duplicate or extend features found in a Windows-based GUI.

WebDataObject (WDO)

On the Web browser client, data is managed within the WebDataObject (WDO), a nonvisual object. The WDO is the client-side equivalent of a server-side SDO.

The WDO manages all visual screen objects that use its data. It manages copies of old values, as well as changed values, in order to know what to submit back to the server-side SDO for record updates.

The WDO facilitates client-side object linking, similar to Progress SmartLinks™ technology.

WebBusinessObject (WBO)

WBO is the primary object for sending data back to the server. It performs the following tasks:

Setting appropriate target information.

Packaging WDO data into hidden form fields.

Assembling lists of server actions.

Note: Do not confuse the WBO with the SmartBusinessObject (SBO). The function of the SBO is to integrate a number of SDOs, whereas the WBO is primarily an object for transferring data to the server.